Method and apparatus of operation considering bandwidth part in next generation wireless communication system

ABSTRACT

The present disclosure relates to a communication method and system for converging a 5th-Generation (5G) communication system for supporting higher data rates beyond a 4th-Generation (4G) system with a technology for Internet of Things (IoT). The present disclosure may be applied to intelligent services based on the 5G communication technology and the IoT-related technology, such as smart home, smart building, smart city, smart car, connected car, health care, digital education, smart retail, security and safety services.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/637,625 filed on Feb. 7, 2020, which is a National Stage Applicationof International Application No. PCT/KR2018/009122 filed on Aug. 9,2018, which claims priority from Indian Patent Application No.201731028486 filed on Aug. 10, 2017, in the Indian Patent Office, thedisclosures of which are incorporated by reference herein in theirentireties.

TECHNICAL FIELD

The disclosure relates to a next generation wireless communicationsystem. More particularly, the disclosure relates to a method andapparatus for operating with considering a bandwidth part.

BACKGROUND ART

To meet the demand for wireless data traffic, which has increased sincedeployment of 4th generation (4G) communication systems, efforts havebeen made to develop an improved 5th generation (5G) or pre-5Gcommunication system. Therefore, the 5G or pre-5G communication systemis also called a ‘Beyond 4G Network’ or a ‘Post long term evolution(LTE) System’. The 5G communication system is considered to beimplemented in higher frequency (mmWave) bands, e.g., 60 GHz bands, soas to accomplish higher data rates. To decrease propagation loss of theradio waves and increase the transmission distance, the beamforming,massive multiple-input multiple-output (MIMO), full dimensional MIMO(FD-MIMO), array antenna, an analog beam forming, large scale antennatechniques are discussed in 5G communication systems. In addition, in 5Gcommunication systems, development for system network improvement isunder way based on advanced small cells, cloud radio access networks(RANs), ultra-dense networks, device-to-device (D2D) communication,wireless backhaul, moving network, cooperative communication,coordinated multi-points (CoMP), reception-end interference cancellationand the like. In the 5G system, hybrid frequency shift keying (FSK) andquadrature amplitude modulation (QAM) (FQAM) and sliding windowsuperposition coding (SWSC) as an advanced coding modulation (ACM), andfilter bank multi carrier (FBMC), non-orthogonal multiple access (NOMA),and sparse code multiple access (SCMA) as an advanced access technologyhave been developed.

The Internet, which is a human centered connectivity network wherehumans generate and consume information, is now evolving to the internetof things (IoT) where distributed entities, such as things, exchange andprocess information without human intervention. The internet ofeverything (IoE), which is a combination of the IoT technology and theBig Data processing technology through connection with a cloud server,has emerged. As technology elements, such as “sensing technology”,“wired/wireless communication and network infrastructure”, “serviceinterface technology”, and “Security technology” have been demanded forIoT implementation, a sensor network, a machine-to-machine (M2M)communication, machine type communication (MTC), and so forth have beenrecently researched. Such an IoT environment may provide intelligentInternet technology services that create a new value to human life bycollecting and analyzing data generated among connected things. IoT maybe applied to a variety of fields including smart home, smart building,smart city, smart car or connected cars, smart grid, health care, smartappliances and advanced medical services through convergence andcombination between existing information technology (IT) and variousindustrial applications.

In line with this, various attempts have been made to apply 5Gcommunication systems to IoT networks. For example, technologies such asa sensor network, MTC, and M2M communication may be implemented bybeamforming, MIMO, and array antennas. Application of a cloud RAN as theabove-described Big Data processing technology may also be considered tobe as an example of convergence between the 5G technology and the IoTtechnology.

In the recent years several broadband wireless technologies have beendeveloped to meet the growing number of broadband subscribers and toprovide more and better applications and services. The second generationwireless communication system has been developed to provide voiceservices while ensuring the mobility of users. Third generation wirelesscommunication system supports not only the voice service but also dataservice. In recent years, the fourth generation wireless communicationsystem has been developed to provide high-speed data service. However,currently, the fourth generation wireless communication system suffersfrom lack of resources to meet the growing demand for high speed dataservices. So fifth generation wireless communication system is beingdeveloped to meet the growing demand for high speed data services,support ultra-reliability and low latency applications.

The fifth generation wireless communication system will be implementednot only in lower frequency bands but also in higher frequency (mmWave)bands, e.g., 10 GHz to 100 GHz bands, so as to accomplish higher datarates. To mitigate propagation loss of the radio waves and increase thetransmission distance, the beamforming, massive Multiple-InputMultiple-Output (MIMO), Full Dimensional MIMO (FD-MIMO), array antenna,an analog beam forming, large scale antenna techniques are beingconsidered in the design of fifth generation wireless communicationsystem. In addition, the fifth generation wireless communication systemis expected to address different use cases having quite differentrequirements in terms of data rate, latency, reliability, mobility etc.However, it is expected that the design of the air-interface of thefifth generation wireless communication system would be flexible enoughto serve the UEs having quite different capabilities depending on theuse case and market segment the UE cater service to the end customer.Few example use cases the fifth generation wireless communication systemwireless system is expected to address is enhanced Mobile Broadband(eMBB), massive Machine Type Communication (m-MTC), ultra-reliable lowlatency communication (URLL) etc. The eMBB requirements like tens ofGbps data rate, low latency, high mobility so on and so forth addressthe market segment representing the conventional wireless broadbandsubscribers needing internet connectivity everywhere, all the time andon the go. The m-MTC requirements like very high connection density,infrequent data transmission, very long battery life, low mobilityaddress so on and so forth address the market segment representing theInternet of Things (IoT)/Internet of Everything (IoE) envisioningconnectivity of billions of devices. The URLL requirements like very lowlatency, very high reliability and variable mobility so on and so forthaddress the market segment representing the Industrial automationapplication, vehicle-to-vehicle/vehicle-to-infrastructure communicationforeseen as one of the enabler for autonomous cars.

DISCLOSURE OF INVENTION Technical Problem

In the existing wireless communication system i.e. in LTE, the bandwidthof the system is limited to 20 MHz and various BW such as 1.4 MHz, 3MHz, 5 MHz, 10 MHz, and 20 MHz are supported. In this LTE, the eNB andUE must support the same BW. However going forward for the 5G systems,considering the wide available BW in mmWave spectrum and other parts ofthe spectrum, there is a lot of scope for freely using the large BW. TheUE and base station (gNB) need not support the same BW and variable BWcapable UE may be supported in such deployments. In order to supportsuch wider BW UE, efficient mechanisms must be studied in order tosupport various operations such as search space configurations,efficient resource allocation mechanisms among others.

Solution to Problem

The present disclosure is designed to address at least the problemsand/or disadvantages described above and to provide at least theadvantages described below. Accordingly, an aspect of the presentdisclosure is to provide a method and apparatus fortransmitting/receiving downlink data in a next generation communicationsystem.

In accordance with an aspect of the present disclosure, a method by aterminal is provided. The method comprises receiving, from a basestation, a radio resource control (RRC) message configuring a ratematching for a physical downlink shared channel (PDSCH); identifying atleast one resource element (RE) where the rate matching is performedbased on the message; and receiving, from the base station, downlinkdata on a PDSCH without the identified at least one RE, by consideringthat the at least one RE is rate matched by the base station, wherein asynchronization signal block (SS block) is transmitted on the at leastone RE.

In accordance with an aspect of the present disclosure, a terminal isprovided. The terminal comprises a transceiver configured to transmitand receive signals; and at least one processor configured to: receive,from a base station, a radio resource control (RRC) message configuringa rate matching for a physical downlink shared channel (PDSCH), identifyat least one resource element (RE) where the rate matching is performedbased on the message; and receive, from the base station, downlink dataon a PDSCH without the identified at least one RE, by considering thatthe at least one RE is rate matched by the base station, wherein asynchronization signal block (SS block) is transmitted on the at leastone RE.

In accordance with an aspect of the present disclosure, a method by abase station is provided. The method comprises transmitting, to aterminal, a radio resource control (RRC) message configuring a ratematching for a physical downlink shared channel (PDSCH); performing arate matching on at least one resource element (RE) identified based onthe message; and transmitting, to the terminal, downlink data on a PDSCHwithout the at least one RE, wherein a synchronization signal block (SSblock) is transmitted on the at least one RE.

In accordance with an aspect of the present disclosure, a base stationis provided. The base station comprises a transceiver configured totransmit and receive signals; and at least one processor configured to:transmit, to a terminal, a radio resource control (RRC) messageconfiguring a rate matching for a physical downlink shared channel(PDSCH), perform a rate matching on at least one resource element (RE)identified based on the message, and transmit, to the terminal, downlinkdata on a PDSCH without the at least one RE, wherein a synchronizationsignal block (SS block) is transmitted on the at least one RE.

Advantageous Effects of Invention

According to embodiments of the present invention, various operationswith respect to the next generation wireless communication system can beenhanced.

BRIEF DESCRIPTION OF DRAWINGS

The above and other aspects, features, and advantages of certainembodiments of the present invention will be more apparent from thefollowing detailed description taken in conjunction with theaccompanying drawings, in which:

FIG. 1 illustrates a various bandwidth involved in a UE's operation.

FIG. 2 illustrates an embodiment of interleaving scheme according to theproposed invention.

FIG. 3 illustrates another embodiment of interleaving scheme accordingto the proposed invention.

FIG. 4 illustrates another embodiment of interleaving scheme accordingto the proposed invention.

FIG. 5 illustrates an embodiment of allocating resources according tothe proposed invention.

FIG. 6 illustrates another embodiment of allocating resources accordingto the proposed invention.

FIG. 7 illustrates embodiments of interleaving schemes according to theproposed invention.

FIG. 8 illustrates another embodiment of interleaving scheme accordingto the proposed invention.

FIG. 9 illustrates an embodiment of activation/deactivation of abandwidth part according to the proposed invention.

FIG. 10 illustrates an embodiment of configuring different RGB sizes forusers according to the proposed invention.

FIG. 11 illustrates an embodiment of a relationship between asynchronization signal and a bandwidth part according to the proposedinvention.

FIG. 12 illustrates another embodiment of a relationship between asynchronization signal and a bandwidth part according to the proposedinvention.

FIG. 13 illustrates an embodiment of configuring a periodicity of ratematching resource according to the proposed invention.

FIG. 14 illustrates an embodiment of activating multiple bandwidth partsaccording to the proposed invention.

FIG. 15 illustrates another embodiment of activating multiple bandwidthparts according to the proposed invention.

FIG. 16 illustrates another embodiment of activating multiple bandwidthparts according to the proposed invention.

FIG. 17 illustrates a flow chart of configuring a control resource setaccording to the proposed invention.

FIG. 18 illustrates a flow chart of configuring an uplink bandwidth partaccording to the proposed invention.

FIG. 19 illustrates an embodiment of configuring an uplink bandwidthpart in TDD system according to the proposed invention.

FIG. 20 illustrates a flow chart of configuring an uplink bandwidth partaccording to the proposed invention.

FIG. 21 illustrates an embodiment of a relationship between bandwidthparts of pcell and scell according to the proposed invention.

FIG. 22 illustrates an embodiment of supporting carriers withoutsynchronization signal blocks according to the proposed invention.

FIG. 23 illustrates a terminal according to an embodiment of theproposed invention.

FIG. 24 illustrates a base station according to an embodiment of theproposed invention.

MODE FOR THE INVENTION

Various embodiments of the present disclosure will be described indetail with reference to the accompanying drawings. In the followingdescription, specific details such as detailed configurations andcomponents are merely provided to assist the overall understanding ofthese embodiments of the present disclosure. Therefore, it should beapparent to those skilled in the art that various changes andmodifications of the embodiments described herein can be made withoutdeparting from the scope and spirit of the present disclosure. Inaddition, descriptions of well-known functions and constructions areomitted for clarity and conciseness. In each drawing, the same orsimilar components may be denoted by the same reference numerals.

Each block of the flow charts and combinations of the flow charts may beperformed by computer program instructions. Because these computerprogram instructions may be mounted in processors for a generalcomputer, a special computer, or other programmable data processingapparatuses, these instructions executed by the processors for thecomputer or the other programmable data processing apparatuses createmeans performing functions described in block(s) of the flow charts.Because these computer program instructions may also be stored in acomputer usable or computer readable memory of a computer or otherprogrammable data processing apparatuses in order to implement thefunctions in a specific scheme, the computer program instructions storedin the computer usable or computer readable memory may also producemanufacturing articles including instruction means performing thefunctions described in block(s) of the flow charts. Because the computerprogram instructions may also be mounted on the computer or the otherprogrammable data processing apparatuses, the instructions performing aseries of operation steps on the computer or the other programmable dataprocessing apparatuses to create processes executed by the computer tothereby execute the computer or the other programmable data processingapparatuses may also provide steps for performing the functionsdescribed in block(s) of the flow charts.

In addition, each block may indicate a module, a segment, and/or a codeincluding one or more executable instructions for executing a specificlogical function(s). Further, functions mentioned in the blocks occurregardless of a sequence in some alternative embodiments. For example,two blocks that are consecutively illustrated may be simultaneouslyperformed in fact or be performed in a reverse sequence depending oncorresponding functions sometimes.

Herein, the term “unit” may include software and/or hardware components,such as a field-programmable gate array (FPGA) and/or anapplication-specific integrated circuit (ASIC). However, the meaning of“unit” is not limited to software and/or hardware. For example, a unitmay be configured to be in a storage medium that may be addressed andmay also be configured to reproduce one or more processor. Accordingly,a “unit” may include components such as software components, objectoriented software components, class components, task components,processors, functions, attributes, procedures, subroutines, segments ofprogram code, drivers, firmware, microcode, circuit, data, database,data structures, tables, arrays, and variables.

Functions provided in the components and the “units” may be combinedwith a smaller number of components and/or “units” or may furtherseparated into additional components and/or “units”.

In addition, components and units may also be implemented to reproduceone or more CPUs within a device or a security multimedia card.

The terms as used in the present disclosure are provided to describespecific embodiments, and do not limit the scope of other embodiments.It is to be understood that singular forms include plural forms unlessthe context clearly dictates otherwise. Unless otherwise defined, theterms and words including technical or scientific terms used in thefollowing description and claims may have the same meanings as generallyunderstood by those skilled in the art. The terms as generally definedin dictionaries may be interpreted as having the same or similarmeanings as the contextual meanings of related technology. Unlessotherwise defined, the terms should not be interpreted as ideally orexcessively formal meanings. When needed, even the terms as defined inthe present disclosure may not be interpreted as excluding embodimentsof the present disclosure.

Herein, a base station performs resource allocation to a terminalExamples of the base station may include an eNodeB(eNB), a Node B,gNodeB(gNB), TRP(Transmission Reception Point), a wireless access unit,a base station controller, a node on a network, etc. Examples of theterminal may include a user equipment (UE), a mobile station (MS), acellular phone, a smart phone, a computer, a multimedia systemperforming a communication function, etc.

Herein, a downlink (DL) is a radio transmission path of a signal from abase station to a UE and an uplink (UL) is a radio transmission path ofa signal from the UE to the base station.

The embodiments of the present disclosure may be applied to othercommunication systems having similar technical backgrounds or channelforms.

For the case of 5G communications, it is proposed that the UE mustsupport bandwidth on the order of 1 GHz in a single carrier manner. Inother words, without using carrier aggregation, a 5G user must supportbandwidths of this order. Several challenges arise in this regard as theuser must support wide bandwidth such as RF, power consumption,scheduling etc. Since a user need not always support such widebandwidth, the concept of 1st and 2nd RF bandwidth were introduced.However the goal is to avoid user from monitoring wide bandwidth all thetime as it is not power efficient. But however, there should be abilityso configure users for such wide bands to support very high data raterequirements. Furthermore, such wide bandwidth is available in above 6GHz bands and hence can be used effectively. In this invention, wediscuss the various bandwidth adaptation aspects for the 5G and futurewireless systems. A FIG. 1 is shown for explanation purposes where thevarious bandwidth (110, 120, 130) involved in the UE operations isshown.

Several aspects of this wideband operation such as configuring searchspace locations, supporting MU-MIMO for different users with differentbandwidth capability sizes, bandwidth indication granularity, resourceblock group size, PRB bundling granularity, bandwidth configurationsetc. have to be addressed. A generic term known as Bandwidth Part (BWP)is defined which indicates a set of contiguous PRBs in frequency domainwhich are configured for a user. Resource allocation will be done withina BWP. Several BWP may be configured to a user but only one will beactivated at a given time instant. Within the BWP, various issuesmentioned above have to be addressed since each BWP is configured in aUE specific manner. Furthermore, when different users are considered forthe case of supporting MU-MIMO in the downlink, the sizes of the BWPsupported by each user must also be accounted for as it impacts thepre-coding design, the channel and interference estimation as a resultof the same etc. BWP is a concept which does not need any RF involvementand it is a layer-1 concept. Multiple BWP may be configured andactivated to a UE and this entails new operations regarding monitoringtimeline, BW sizes supported etc. These above mentioned issues will bedescribed hereinafter in detail.

Resource allocation considering BWP

FIG. 2 illustrates an embodiment of interleaving scheme according to theproposed invention. Considering UE-specifically configured BWPs, thefollowing two solutions may be considered in order to adopt downlink(DL) resource allocation (RA) type 2 with distributed VRB-to-PRB mappingwhich was already specified in LTE as shown in FIG. 2.

-   -   Common Interleaving (210): All BWPs/UEs share single        interleaving        -   Cons: Interleaved VRBs cannot be confined within configured            BWP    -   BWP-specific interleaving (220): Interleaving is generated        within each configured BWP        -   Cons: PRB collision between different BWP-specific            interleaving

If common interleaving is performed for all UE as shown in figure above,it is seen that the VRB-to-PRB mapping may force the PRBs of one UE tobe located outside the actual BWP active for this user which cannothappen as the user must operate only within its active BWP. IfBWP-specific interleaving is supported, then collisions can happen sinceindependent interleavers may be used for different users without anycoordination. Hence, some unified mechanisms are proposed below totackle the issues. Similar or same mechanisms can be adopted for uplink(UL) resource allocation if distributed mapping is used for the case ofUL.

Option-1: Group Based BWP-Specific Interleaving

FIG. 3 illustrates an embodiment (option 1) of interleaving schemeaccording to the proposed invention. Since RA-type 2 invented to reducesignaling overhead needs a chunk of contiguous resource blocks to beallocated in VRB domain, if BWP-specific interleaving which isindependently generated per BWP is used, VRBs allocated for other UEsare scattered within BWP for some UE as shown in FIG. 3. Thus,contiguous VRBs larger than resource block size to be allocated may notbe found for the UE. It may lead to degrade the flexibility ofscheduling and waste frequency resource from gNB perspective (310). Toresolve the scattered VRB issue for BWP-specific interleaving,group-based BWP-specific interleaving is proposed. For this technique,three conditions are given to design the interleaving as follows:

Condition-1) For all PRBs within DL or UL system BW, distributed PRBsare grouped into disjoint M groups and the grouping is common for allUEs.

Condition-2) For all VRBs within each BWP, contiguous VRBs are groupedinto disjoint M groups.

Condition-3) Per BWP, the number of VRBs is equal to the number of PRBsbelonging to the same group

Under above mentioned conditions, group based BWP-specific interleavingconsisting of one-to-one VRB-to-PRB interleaving happens within eachgroup is carried out.

One way to implement the interleaving satisfying with above conditionsis to utilize block interleaving structure (320). Although blockinterleaving is already well-known and widely used, in order to apply togroup based BWP-specific interleaving, several constraints should betaken into account. In case of block interleaving with row-by-rowwritten and column-by-column read out, a column can be regarded as agroup. Thus, although it was designed in LTE that the number of columnsis associated with the total number of VRBs, it is proposed thatregardless of respective BWP size, all BWP-specific block interleaversmust have M columns at a given time instance. Moreover, when the numberof VRBs may not be a multiple of M in a BWP, condition-1 may not holdaccording to where nulls are inserted as well. Therefore, to keep thecondition-1, it is proposed to force to insert nulls always from lastcolumn of the last row. Details and figure to generate the interleavingare described below.

FIG. 4 illustrates another embodiment of interleaving scheme accordingto the proposed invention. It is assumed that both VRB and PRB indexingare performed from bottom frequency to top frequency without loss ofgenerality. When the number of VRBs within a BWP is denoted as N_(VRB)^(BWP), the VRB number N_(VRB)=0, . . . , N_(VRB) ^(BWP)−1 isinterleaved to n_(PRB) number as equation 1:

$\begin{matrix}{{n_{PRB}\left( n_{VRB} \right)} = \left\{ {\begin{matrix}{{{M\left( {n_{VRB}\mspace{14mu}{mod}\mspace{14mu} N_{group}} \right)} + \left\lfloor \frac{n_{VRB}}{N_{pump}} \right\rfloor},} & {n_{VRB} < {\left( {M - N_{cell}} \right)N_{group}}} \\{{{M\left( {n_{VRB}^{\prime}\mspace{14mu}{mod}\mspace{14mu} N_{group}^{\prime}} \right)} + \left\lfloor \frac{n_{VRB} - 1}{N_{group}^{\prime}} \right\rfloor},} & {Otherwise}\end{matrix},{{{where}\mspace{14mu} N_{group}} = \left\lceil \frac{N_{VRB}^{BWP}}{M} \right\rceil},{N_{group}^{\prime} = {N_{group} - 1}},{N_{soft} = {{MN}_{group} - N_{VRB}^{BWP}}},{{{and}\mspace{14mu} n_{VRB}^{\prime}} = {n_{VRB} - {N_{group}\left( {M - N_{soft}} \right)}}}} \right.} & \left\lbrack {{equation}\mspace{14mu} 1} \right\rbrack\end{matrix}$

The number of groups M may affect between interleaving performance andscattered VRB interference. If M is increased, more distributedallocations can be possible, but interleaving performance is reduced.Therefore, the number of groups M can be fixed as well as configured viasystem information, RRC, or (group-)common PDCCH. The procedure is shownin FIG. 5 below to configure M.

FIG. 5 illustrates an embodiment of allocating resources according tothe proposed invention. A gNB configures the number of groups M for theUE via SI (system information), RRC signaling, or (group-)common PDCCH(510). And, the gNB also configures a BWP for the UE (520). By theconfigured M and BWP, the UE generates an interleaver to be used withinthe BWP (530). After transmitting a DCI (downlink control information)including RA type 2 with distribute mapping to the UE (540), the gNBtransmits scheduled data on a PDSCH (physical downlink shared channel)(550). The UE decodes the received data by using the generatedinterleaver (560). The following FIG. 6 shows a gNB operation to decideappropriate M to be configured. FIG. 6 illustrates another embodiment ofallocating resources according to the proposed invention. The gNBdetermines the number of overlapped BWPs K for the value M (600) andcompares the K with a predetermined threshold value A (610). If K>A, thegNB increases the number of groups M (630) and reconfigures the updatedM to all UEs via SI or RRC signaling (632). And threshold values A and Bare updated according to the updated M (634). However, If K<=A, the gNBcompares the K with another threshold B (620). If K>=B, the gNB updatesthe current number of overlapped BWPs K (650). If K<B, the gNB decreasesthe number of groups M (640) and reconfigures the updated M to all UEsvia SI or RRC signaling (642). And the threshold values A and B areupdated according to the updated M (644).

Option-2: Common Segmented Interleaver

-   -   If small size of segmented interleaver, frequency diversity is        degraded    -   If large size of segmented interleaver, some small BWP cannot        contain the interleaver    -   Segmented interleaver size may be configured by SI, or RRC    -   No additional indication

Option-3: BWP-Specific Multiple Interleavers

-   -   Multiple BWP-specific interleaver configuration to UE    -   If collision happens, NW use another interleaver, then indicate        it to UE    -   Can provide DoF for scheduling

FIG. 7 illustrates embodiments (option 2-710 and option 3-720) ofinterleaving schemes described above.

Option-4: BWP-Specific Interleaving as a Function of Slot Number(Similar to Search Space Design)

-   -   Interleaver is changed according to slot number    -   If collision happens at n-the slot, no collision may happen at        n+1-th slot    -   Can provide DoF for scheduling    -   No indication (Pre-defined interleaver)

Option-5: Support different interleavers for one UE within its BWP i.e.,BW region specific interleaving and support multiple interleavers forwideband UE. This is similar to BW region specific PRG size definition.

-   -   Within BWP of UE 1, use common interleaver—based on C-RNTI or        some UE_ID like UE specific search space    -   Outside BWP of UE 1(but within the BWP of another UE) use a        different interleaver    -   To reduce signaling overhead, a set of interleavers can be        defined and the interleaver index be sent to the UE    -   Signal PRB start; PRB stop index and the interleaver index to        the UE

FIG. 8 illustrates another embodiment (option 5) of interleaving schemeaccording to the proposed invention. Various interleavers (810, 820,830) are supported for the UE 1 and each of the interleavers (810, 820,830) is defined for a specific BW region.

Option-6: Avoid distributed mapping/DL resource allocation type-2 whenoverlapping BWP exist

-   -   Since defining interleavers can get complicated when more than2        users BWP overlap i.e., if UE1, UE2 and UE3 BWP are overlapping;        the gNB may take a decision to avoid distributed mapping in such        cases.

Option-7: When overlapping may occur (as gNB knows about overlap);signal an offset in terms of PRBs to a UE in case gNB identifies thatthe used interleavers are causing an overlap/collision between theusers. In other words, after VRB-PRB mapping done by gNB, if itidentifies there is a potential collision across users, signal an offsetto be used by a UE for its final mapping.

-   -   Offset=0 means continue using the same RB allocations after        interleaving. Offset=+1(−1) means shift by 1 PRB up (down) in        frequency. It can be some length of bits defined to support        distributed mapping.

Each of the embodiments above can be indicated to the UE by the gNB viaUE specific signaling—via RRC/L1/SI. L1 signaling is dynamic and cansupport efficient MU-MIMO techniques. Different options may be used indifferent slots to randomize the interference, channel impacts and gainbenefits of all possible options.

Activation/De-Activation of BWP

RRC signaling based activation and de-activation is supported for 5Gsystems as it is naturally extendable from configuration to activationmechanisms. Between DCI and MAC mechanisms, there is a tradeoff betweenthe signaling reliability of MAC versus fastness of DCI-based signaling.Among MAC and DCI, DCI signaling can be preferred for BWP activation.Although a DCI is missed, some fallback behaviors can be mentioned, Evenin LTE when a DCI is missed, some timers are activated based on whichthe UE monitors some fallback DCI. Similar behavior may be defined.Specifically, the following behavior may be defined for the UE—

-   -   If DCI missed; after timer1 expiry go back to initial BWP where        the UE existed before    -   If nothing found i.e., no DCI found after timer2; go back to        default BWP which is configured by the gNB to the UE

Hence a DCI mechanism along with timer behavior can be used foractivating BWP in 5G systems and to get full benefits of the BWPtuning/re-tuning and BW adaption. A time-pattern based mechanism mayalso be supported for the BWP activation mechanisms. In here, a timepattern similar to SPS(semi-persistent scheduling)/DRX(discontinuousreception) mechanism and avoids much signaling. If time pattern ismissed, then the UE will go to default BWP. If some conflict happensbetween the time pattern and the DCI based signaling, then the UEfollows the DCI based signaling with higher priority.

The time pattern can be with respect to slot timing/subframetiming/SFN-based/SS block timing as a reference etc. An event-basedactivation of BWP seems attractive rather than keeping a wider BWPactive when it is not needed. An OnDuration timer may be defined todecide how long a BWP which is wide is turned no and an InactivityTimerafter which the UE moves to narrow BWP after some period of inactivity.

FIG. 9 illustrates an embodiment of activation/deactivation of abandwidth part according to the proposed invention. When an event istriggered (910), gNB signals event based OnDuration and InactivityTimervalues to UE. Or, the values can be fixed in specification (920). The UEmoves to wider BW for a time indicated by OnDucation from the gNB (930),and the UE moves to narrower BW after InactivityTimer indicated from thegNB expires inside the wider BW (940).

MU-MIMO Impacts

The PRG size may depend on RBG (resource block group) size, or othervalues based on bandwidth part, and/or scheduled bandwidth and/or UEcapability. In LTE, the PRG size was defined based on the RBG sizes asit was more appropriate to define the pre-coding vectors. A similardesign may be followed in NR. Since the RBG size may depend on theconfigured BWP sizes (as indicated earlier and may be indicated viaDCI), the PRG size may directly or indirectly depend on the configuredBWP size. Of course it must be taken care to consider the case ofmultiple BWP configurations. Furthermore, when a WB(wideband) andNB(narrowband) UE are multiplexed for MU-MIMO purposes, the PRG sizesmay be defined commonly for both these UEs and be indicated via UEspecific signaling. For instance, in LTE when the RBG size was 3, thePRG size 3 was chosen over 2 to have scheduling flexibility. Similarly,the PRG sizes of both WB and NB UE must be taken into account and theappropriate PRG size may be chosen and indicated. The gNB may ensurethat the pre-coding vectors are common across the two users such thatchannel estimation can be done. For instance if User 1 uses PRG size Xand user 2 uses PRG size Y, then precoding for MU-MIMO can be definedover an allocation of size of the equation 2 below in order to ensurereliable channel and interference estimation over LCM(X,Y) PRG.

Precoding Granularity=LCM(X,Y)   [equation 2]

This design can be followed for the case of MU-MIMO across differentnumerologies or MU-MIMO across users with different BWP sizes. Othermethods can be to support the PRG size based on the lowest PRG sizesupported by each user or the following equation 3.

Precoding Granularity=min(X,Y) or max(X,Y) or X or Y   [equation 3]

Another solution could be wherein a common PRG size is used only withinthe BW region where there is an overlap between the multiple users andthen in other regions different PRG sizes may be used. This can helpwhen UE1 BWP partially overlaps with 2 different users UE2 and UE3 eachhaving different BWP sizes as shown in FIG. 10.

FIG. 10 illustrates an embodiment of configuring different RGB sizes forusers according to the proposed invention. In FIG. 10, different PRGsizes (1010, 1020, 1030) are used for each BWP regions.

Different PRG sizes can be used in a BW region specific manner. Sointerference and channel estimation can be done in a BW region specificmanner within the BWP of each UE. PRG size 3 is common for UE 1 and UE 3within their overlap region. Similarly PRG size 1 is common for UE 1 andUE 2 within their overlap region. Therefore, the following equation 4can be defined.

Precoding Granularity=function(BW region location, number of users in BWregion, BW region size)   [equation 4]

These can be explicitly indicated to the UE via gNB signaling via L1/RRCi.e. UE specific signaling.

SS and BWP Relationship

By definition, a BWP will have only one numerology throughout all of itsRB's. This active BWP may or may not contain an SS block. While a UE maybe activated with multiple BWPs, it may be possible that one of thesecontains SS block or none may contain the SS block. Depending on whetheror not the activated i.e., monitored BWP have SS block, UE will beconfigured for retuning to support measurements of the same. Thefollowing issues may arise in terms of the configuration of the SS blockand the BWP for a UE.

For example, SS block has a numerology of 30 kHz, and located in RBindex 10˜15. Assume that BWP1 is configured from RB index 0˜9 (notincluding SS blocks), and BWP2 is configured from RB index 0˜30. (i.e.,including SS blocks). It should be determined that a BWP1 be activatedwith SCS=15 kHz or 30 kHz. Also, whether BWP2 be activated with SCS=15kHz or 30 kHz also needs to be determined. If so, how to treat RB index10˜15, is Rate-matching necessary, and SS blocks can be a part of BWPshould be determined. This issue is shown in the FIG. 11.

FIG. 11 illustrates an embodiment of a relationship between asynchronization signal block (SS block, 1130) and a BWP 1(1110) and BWP2(1120) according to the proposed invention.

This issue also depends on the UE capability information whether or notit can support multiple numerologies simultaneously. Then it can supportSS block and the data/control channels with different numerology withina same BWP. Else, from one UE perspective the SS block is configuredwith numerology 1 and for another UE perspective the data/control may beconfigured with a different numerology. Both will be sent at a same timeinstant. The slot structure for each of them assumed will be differentdue to different numerology. For example, 16 symbols of 240 kHznumerology corresponds to 1 symbol of 15 kHz numerology. Accordingly thegNB can schedule the users or even a single user if it can support it.

The UE reading PDSCH must be indicated the location of the SS block (ifpartial overlap occurs, then more indications are needed indicating howmuch of SS block is overlapping with the mentioned BWP, hence it iseasier if the entire SS block is within the BWP and the gNBschedules/configures BWP in such a manner; however if need arisespartial overlap with SS block BW is also allowed with appropriatesignaling indicated to the UE about the number of RBs of SS blockoverlapping with the PDSCH.) These are shown in FIG. 12.

FIG. 12 illustrates another embodiment of a relationship between asynchronization signal and a bandwidth part according to the proposedinvention.

BWP1 can be activated with 30 kHz easily without guard bandrequirements. BWP1 with 15 kHz may need guard band configuration toavoid potential leakages between different numerologies. BWP2 can beactivated with 30 kHz by default. For 15 kHz, the gNB must take care ofdoing filtering, have 2 FFT blocks to generate data as suchsimultaneously i.e., supporting 2 numerologies together etc. This is gNBimplementation details.

When a BWP has same SCS as SS block (either fully included (1220) orpartially included (1230)), no issues are seen. Either a UE is ratematched around the SS block if it doesn't need the SS block or it willuse the SS block for measurements while PDSCH is FDM'ed in the left overregion for which rate matching may not be needed when it can beindicated to UE via distributed resource allocation mechanisms (forexample, this can be done during RRM measurement gaps where UE uses SSblock for RRM measurements and also receive some PDSCH in the remainingBW i.e., minimum UE BW minus SS block BW).

When contiguous resource allocation mechanisms are used, then explicitindication of the rate matching resources must be provided. These areseparate resources to indicate where the UE must do rate matching. Notethat rate matching of a PDSCH around PBCH region has been allowed inLTE, so that the network can transmit PDSCH in both the partial slot (inthe PBCH BW) and full slot (in the non-PBCH BW) without involving newscheduling indication method and/or without introducing any schedulingrestriction. In legacy LTE, no indication was necessary as there is asingle PBCH region in a cell. In 5G, a semi-static or a cell-specificindication of the SS block resources could be sufficient for UE to ratematch the PDSCH around the SS block. This is needed because 5G cansupport multiple SS blocks. Rate matching and resource allocation can bea) separately handled b) jointly handled. For separate handling,separate resources must be allotted for indication of this ratematching. For joint indication, improved resource allocation mechanismsare needed.

When a BWP can have different SCS compared to SS block (1210, 1240) butthe UE will not monitor the SS block (simultaneously) when it uses thisBWP (considering a UE can monitor only one SCS at a time), can bepossible by ensuring that there is no leakage between the multiplenumerologies and the guard sub-carriers are either indicated to the UEor indicated as reserved resources or avoided in the resourceallocations mechanisms.

Hence, the following decisions and indications must be taken by gNB andindicated to UE:

-   -   whether BWP and SS block overlapping or not    -   whether BWP and SS block have same numerology    -   whether Rate matching needed around SS block    -   whether Guard subcarriers to be indicated when BWP and SS block        have different numerology

This decision must be done for PDCCH, PDSCH, both for broadcast andunicast ones.

For rate matching following information is needed for the UE:

-   -   Actually transmitted number of SS blocks per SS block location        (among multiple SS blocks)    -   Total number of SS blocks locations (in terms of frequency        location) within a bandwidth region configured for the UE    -   Periodicity value per SS block (at a given frequency) within a        BW region configured for the UE    -   Periodicity values for the rate matching resources that match        the periodicity of the SS block (s) both for within serving cell        and for neighbor cell measurements

This indication can be via RMSI/RRC signaling/via RRC connectionsetup/DCI.

RRC signaling seems sufficient as things may only change in semi-staticmanner The RRC signaling format may be represented as FIG. 13. FIG. 13illustrates an embodiment 1310 of configuring a periodicity of ratematching resource according to the proposed invention.

Apart from these, the following factors also impact the rate matchingfor PDSCH—DMRS (demodulation reference signal) locations for PDSCH—onesymbol or 2 symbols front-loaded in OFDM symbol 2 or 3 for slot-basedscheduling; DMRS location for PDSCH in mini-slot scheduling—1st OFDMsymbol of scheduled data location will also be indicated to UEexplicitly to account for rate matching. In addition, the SS blockmappings have been agreed to be in OFDM symbols 2,3,4,5 or 4,5,6,7depending on the numerology and patterns allowed. In such cases, theseOFDM symbols must be taken into account for the case of rate matching aswell. The PSS and SSS are 12 PRBs inside an SS block while SS blockentire BW is 24 PRBs. If the 12 PRBs of the SS block will be used forthe data can also be indicated to UE and will impact the rate matchingindications.

Multiple Active BWP

FIG. 14 illustrates embodiments of simultaneously activating multiplebandwidth parts according to the proposed invention. For the case when aUE can support multiple numerologies the above situations can besupported for allowing multiple simultaneously active BWP for a UE. Formultiple active BWP, cross BWP scheduling is allowed for future wirelesssystems (FIG. 14(a)). CSS is there in one of them and is configured byNW and indicated by RRC. USS is present in each of them—can havescheduling/switching DCI—either combined or separate. The design forcombined or separate DCI for scheduling and switching is discussedlater.

If both BWP are received together, in other words if both BWP areactivated at the same time instant, then buffering is needed so that theUE can receive data on other BWP also and allow for the other BWP tocarry data (FIG. 14(b)). This depends on UE capability of buffering datafrom other BWP and must be indicated to the gNB via RRC connectionsetup. After DCI decoding on one BWP and getting indication of PDSCH onother BWP, UE recover data from buffer which is possible if data startsafter end of DCI reception. Therefore number of simultaneously activeBWP depends on UE capability, DCI design, buffering ability etc. Inmethod 3 (FIG. 14(c)), it is shown that the switching and scheduling DCIare in different BWP. In such cases, each DCI must be indicated aboutthe DMRS locations among other parameters. For instance, the schedulingDCI may not follow slot based scheduling and instead be on a mini-slotlevel because of its location in time. Then there is dynamic switchingbetween slot and mini-slot based scheduling. For this switching,additional indication for the scheduling DCI which is based on mini-slotbasis will need DMRS signal locations. For slot-scheduling DMRS isfront-loaded. For mini-slot/symbol level scheduling for the case ofscheduling DCI DMRS locations have to be indicated either via RRC or L1signaling. Since this BWP activation etc. happens on a fast scale via L1signaling, it is preferred that this signaling also follows L1 based.Having separate scheduling DCI can easily help to schedule several BWparts without much overhead—from forward compatibility perspective itseems better, this overhead can be more and may overload the L1signaling. Hence, considering the overhead, joint DCI for bothscheduling and switching may be preferable.

Search Space Configurations Parameters Across BWPs

Parameters such as CCE, CCE-REG mapping, REG bundle, REG interleavingetc. may be assumed to be same by the UE across BWPs. Else they will beindicated via UE specific signaling. In order to maintain some signalingoverhead reduction, only the parameters changed across the BWPs may beindicated to the UE. Hence, some parameters may be same across BWPs andsome parameters may be different. The following may be indicated to UEseparately for CSS and USS CORESETs (control resource sets).

For a given search space—a) CORESET parameters are same across all BWPsb) some CORESET parameters are common across BWPs and c) none of theCORESET parameters can be assumed to be same across BWPs. Option c (noneof the CORESET parameters can be assumed to be same across BWPs) willrequire additional signaling whenever a CORESET is configured in a BWPand may be avoided for faster L1 signaling to support BWPactivation/de-activation/adaption etc.

Another UE behavior may be defined as follows for the case of CORESETparameters across BWPs (both for CSS and USS)

a) Behavior 1: Assume same irrespective of numerology and BWPconfigurations

b) Behavior 2: Assume same only if the numerology of BWPs are sameirrespective of other BWP configurations

c) Behavior 3: Assume different configurations irrespective ofnumerology or BWP size or etc.

d) Behavior 4: Assume same only if the numerology of BWPs and the BWPsizes are same

e) Behavior 5: Assume same only if the numerology of BWPs are same butthe BWP size is different

f) Behavior 6: Assume same only if the size of BWPs are same but thenumerology is different

g) Behavior 7: Assume same only if the starting location of the BWPs issame irrespective of other parameters

h) Behavior 8: Assume same only if the starting location of the BWPs andsize of BWPs is same irrespective of other parameters

i) Behavior 9: Assume same only if the starting location of the BWPs andnumerology of BWPs is same irrespective of other parameters

Switching and Scheduling DCI—Separate DCI vs. Joint DCI for BWPactivations for cross BWP scheduling

-   -   Single DCI for switching +scheduling        -   1 long DCI format    -   Separate DCI for switching and scheduling        -   2 small DCI formats

This design impacts detection probability, complexity and UEimplementation/power consumption and flexibility of scheduling the BWPs.

-   -   Long DCI format can be        -   more reliable and better detection performance        -   Saves CRC check for the UE and reduces CRC overhead        -   Saves resource and spectral efficiency        -   Less flexible as to change some small parameters; one of the            shorter DCI formats may remain same and indicated to UE            while only the scheduling DCI may be changed. But in longer            DCI format entire thing needs to be changed and again            decoded by the user.        -   For polar codes, longer DCIs are better as they can benefit            from coding gains (i.e. ‘overhead’ per bit sent is lower for            longer DCIs (and of course, the same applies for the CRC            overhead). There is some power benefit from the shorter DCI            but relative to the overall UE power consumption for blind            decoding's, it is probably rather negligible —may depend on            implementation if there is any at all and may be same as            long DCI formats.    -   Short DCI formats (2 of them separate for scheduling and        switching)        -   More blind decodes if the 2 DCI formats are of different            size        -   More blind decodes if both of them are in different BWP        -   BD (blind decode) can be maintained if the location of one            of them is fixed; indicated via another for which BD is done        -   BD can be maintained if same size of each DCI with one extra            bit to identify which DCI is what, but both these should be            inside the same BWP        -   More flexible as compared to longer DCI format

Therefore configuration of the long DCI format i.e., joint DCI formatfor switching and scheduling versus separate DCI format individually foreach of them can be configurable by the gNB signaling to the UE. Thiscan be per UE, depending on BWP (i.e., BWP specific), frequencyspecific, and BW size specific configurations among others.

There are few mechanisms to reduce the blind decoding overhead for thecase of the separate DCI formats

-   -   For a long DCI format        -   A start CCE index may be configured within every BWP if the            UE needs to be scheduled on some other BWP        -   If UE finds something at a specific CCE index x start            location; then it can be interpreted as the scheduling            information for the BWP x        -   Multiple BWP can be scheduled with PDCCH mapped to 2            candidate CCE locations (i) and (j)        -   If none of the candidate locations (mentioned above) have a            probable DCI format OR have all 0's present in those            locations; then that means the same BWP is used for            scheduling and no switching is needed    -   For short DCI formats with separated DCI        -   Linking scheduling DCI location via switching DCI reduces            blind decodes i.e., once a switching DCI is found via BD            mechanisms, the UE will know where in the target BWP the UE            must look for the scheduling DCI        -   Fixed location of scheduling DCI for a given BWP depending            on the BWP identifier which can be explicit id or start RB            index or center frequency of the BWP

FIG. 15 illustrates another embodiment of activating multiple bandwidthparts according to the proposed invention. In FIG. 15, box 1 indicatesthe switching DCI; boxes 2 and 3 indicate the scheduling DCI fordifferent BWP. Fixed locations for the box 2 and 3 based on BWP arebeing used for scheduling and indicated via switching DCI i.e., box 1.For example to switch to BWP2, UE will go and check a fixed box 2location and for BWP3 to switch UE will go and monitor the box 3location. If some data found regarding the 2nd location, UE will switchto BWP2 and use the scheduling information found there. In the FIG. 15three techniques are shown wherein the 1st figure on left side (FIG.15(a)), the switching and scheduling DCI are both inside the same BWPwhich happens when the switching DCI does not indicate anything to theUE for switching. For the middle figure (FIG. 15(b)), the switching DCIdirectly indicates the UE to go to a different BWP and then UE readsscheduling DCI inside that BWP. For the right side figure (FIG. 15(c)),switching and scheduling DCI are in same BWP but the scheduling DCI fordifferent BWP is located at some pre-defined locations based on which UEwill use it in next time instant.

For the case of BWP scheduling including cross-BWP scheduling; followingDCI formats may be considered:

a) Long DCI format containing switching and scheduling indications oftarget BWP

b) Separate DCI format for scheduling and switching wherein

-   -   1. Scheduling and switching DCI are in source BWP and        -   1.1 Switching DCI explicitly points to the location of            scheduling DCI        -   1.2 Switching DCI indicates BWP id and this id can be used            to identify location of scheduling DCI for the target BWP;            id can be center frequency, start RB location or explicit ID            based on all the BWP configured to a UE    -   2. Switching DCI is in source BWP and scheduling DCI is in        target BWP; this scheduling DCI location inside the target BWP        can be blindly decoded or explicitly indicated to the UE via        switching DCI

CORESET Configurations

FIG. 16 illustrates another embodiment of activating multiple bandwidthparts according to the proposed invention. Various CORESETconfigurations can be defined considering different numerologies asshown in FIG. 16.

-   -   CORESET configuration for MIB in SI    -   CORESET configuration for paging and RAR (random access        response) in RMSI(remaining system information)    -   Same CORESET configurations for entire initial access    -   CORESET configuration for paging indicated via RACH (random        access channel) procedure    -   CORESET configuration for CSS/USS for connected mode UE        indicated via        -   RRC indicate to UE about CSS/USS numerology and location        -   USS/CSS has fixed numerology irrespective of BWP            -   USS/CSS parameters can be fixed (OR)            -   USS/CSS configuration parameters other than numerology                are indicated by RRC

When the CSS (1630) and PDSCH (1610, 1620) have different numerologiesas shown in FIG. 16, rate matching of PDSCH must be done along withguard subcarriers if needed to support any leakage across the differentnumerologies. In the FIG. 16 shown are the BWP for different UEs (1610,1630) which are overlapping and configured with different numerologies.These numerologies could be different from the numerology configured forthe case of the search space. The gNB to UE signaling is shown in theflow chart below and the decision making procedure is also indicated inthe flow chart shown in FIG. 17.

FIG. 17 illustrates a flow chart of configuring a control resource setaccording to the proposed invention. For a UE in idle state (1710), aCORESET can be configured via MIB (master information block) and/or RMSI(1720). Or, a UE which is not in idle state, i.e., RRC connected or RRCinactive state, a CORESET can be configured via SI/RRC signaling from agNB, or the CORESET can be fixed in specification (1730). If anumerology for a CSS is indicated by RRC (1740), the UE overrides theconfiguration of SI/RRC/fixed specification (1750). However, anumerology for a CSS is not indicated by RRC signaling, the UE usesdefault configuration for a CSS (1760).

For the case of multiple active BWPs, the possibility of a CORESET beingsplit across the multiple active BWP can be explored. For instance thegNB can configure the number of blind decodes per BWP. Some of theAL(aggregation level)'s (for example 1 and 2) can be configured only inone BWP and some of the remaining AL's (for example 4 and 8) can beconfigured in another BWP. If decoding succeeds in some AL, then the UEneed not look in another BWP.

UL BWP Configuration

FIG. 18 illustrates a flow chart of configuring an uplink bandwidth partaccording to the proposed invention.

One of the main questions to answer is when the UL BWP is configured toa user. For the case of PRACH (physical random access channel), theresources are already indicated to the user via RACH configuration(1810). The next time UL BWP is needed is for the PUCCH (physical uplinkcontrol channel) to send SR (scheduling request) when UE has UL data tosend (1820). Else the UE will receive any other configuration via the ULgrant. Hence, the earliest stage when the UE needs UL BWP configurationis via the RRC connection setup configuration. Before that UL BWPconfiguration is not needed. A default UL BWP may be defined to the userwhich it can use for purposes where no UL configurations are indicatedto the UE (1830). Else, it can send PUCCH on the BWP configured withPUCCH resources. If the default UP BWP is not configured, UE shouldperform PRACH and get the configuration for the UL BWP again (1840).

The various locations where UE is indicated the UL BWP configurationsare:

a) MIB

b) RMSI

c) RACH Configuration

d) RAR

e) Msg4

f) RRC Connection Setup

Via RRC connection setup seems preferable and sufficient. At leastdefault UL BWP configurations can be done via these above channels.

For TDD mode; if UL BWP is different/changes from the DL BWP; then theGP between DL to UL should include additional time to allow forretuning/changing BWP and the TA value difference. For same BWP centerfrequency, the GP can be less time. For different BWP center frequencyGP time should be more. To account for all; UE capability informationbased GP be designed and indicated to UE. But since frame structureshould support all NR UE; assume a max change in re-tuning timeline anddesign GP based on the max time needed for UL BWP changing. FIG. 19illustrates the above described embodiment of configuring an uplinkbandwidth part in TDD system according to the proposed invention.

PUCCH resources in a BWP can be located anywhere inside the BWP forCP-OFDM waveform and edges of the BWP for the case of DFT-s-OFDMwaveform in order to maintain the single carrier properties. PUCCHfrequency hopping may be supported within and across BWPs. The PUCCHresources can be identified within the same BWP (if the UL and DL BWPsare same) by using a parameter n_(CCE) similar to LTE which isindicating an offset from the PDCCH configured in that BWP. For the caseof the different BWP, this offset can include the BWP id and then anoffset form the starting RB location of the UL BWP. Hence followingmechanisms can be used for indicating the PUCCH resources via a formulasimilar to the equation 4 below:

n ⁽¹⁾PUCCH=n _(CCE) +N ⁽¹⁾PUCCH   [equation 4]

N⁽¹⁾ _(PUCCH) is the statically configured resources typically used forformats 2/2a etc. For the rest of PUCCH resources, the UE can beindicated via one of the following mechanisms:

a) Within the same BWP use LTE mechanism, offset form PDCCH location vian_(CCE) and N⁽¹⁾ _(PUCCH) indicated by higher layer signaling.

b) Across BWPs, the offset n_(CCE) can be expressed from PDCCH withinthe source BWP and the start RB index of the target BWP

c) Across BWPs, n_(CCE) indicates the offset from the start RB index oftarget BWP

d) Explicit offset indication to the UE via RRC/L1

FIG. 20 illustrates a flow chart of configuring an uplink bandwidth partaccording to the proposed invention.

The number of RB's that can be used for PUCCH transmission within a BWPis determined by N^(PUCCH) _(RB) which can be configured at RRCconnection setup stage since BWP is configured to UE only then (2010).This parameter can be BWP specific. More specifically, this isconfigured per UL BWP. A single UE is given multiple PUCCH resources—astandard PUCCH resource and an SR PUCCH resource per UL BWP (includingdefault UL BWP) (2020, 2030). Standard PUCCH resource is used when HARQ(hybrid automatic repeat request) is transmitted without SR and SR PUCCHresource is used when sending SR with/without HARQ per BWP. The numberof statically reserved PUCCH resources are configured per BWP andindicated via RRC signaling along with BWP configuration to a UE. ForPUCCH formats which transmits HARQ feedback for a PDSCH transmission onthe BWP where there is no corresponding PDCCH detected (as in the SPScase), instead of nCCE and n1PUCCH-AN, N1PUCCH-AN-Persistent should beused for determining PUCCH resources. It is one value out of 4N1PUCCH-AN-PersistentList which is based on TPC (transmission powercontrol) command received in the DCI format and indicates asemi-persistent downlink scheduling activation.

BWP are configured in UE specific manner. Hence PUCCH sharing may not benecessary for the users when BWP are configured in such a manner.However, when BWP overlap across users, then UE's can share the PUCCHRB's but the combination of orthogonal codes and cyclic shift is uniquefor each UE via a parameter n⁽¹⁾ _(CS). This sharing may be necessaryonly when DFT-s-OFDM is used as they may be configured at edge of theBWP for single carrier properties sake and such a region may overlapwith other users in case of BWP overlapping. However for CP-OFDMwaveform as in short-PUCCH case, the resources can be multiplexedwithout any issue.

Following is an example for RRC Connection Reconfiguration message:

   message c1 : rrcConnectionReconfiguration : {  

 cqi-ReportPeriodic setup : {  cqi-PUCCH-BWPIndex cqi-PUCCH-ResourcePerBWPIndex  cqi-PUCCH-DefaultBWPIndex cqi-PUCCH-ResourcPerDefaultBWPIndex  cqi-PUCCH-ResourceIndex 12, cqi-pmi-ConfigIndex 8,  cqi-FormatIndicatorPeriodic widebandCQI : NULL, ri-ConfigIndex 483,  simultaneousAckNackAndCQI TRUE  }  },   .. ...  schedulingRequestConfig setup : {   sr-PUCCH--BWPIndex  sr-PUCCH-ResourcePerBWPIndex   sr-PUCCH-DefaultBWPIndex  sr-PUCCH-ResourcePerDefaultBWPIndex   sr-PUCCH-ResourceIndex 0,  sr-ConfigIndex 97,   dsr-TransMax n4   }   } }

indicates data missing or illegible when filed

This message shows how the PUCCH resources may be configured to UE perBWP, within default BWP, or in a generic fashion.

For the case of PUSCH (physical uplink shared channel) configurations, aUE may be configured for frequency hopping within a BWP and across BWP.For hopping therefore a UE is configured with 2 parameters as (N_(RB)^(HO) and N_(BWP) ^(HO)) which indicate the hopping RBs within a BWP andthe BWP to which the UE should hop to. Instead if N_(SB) in LTE, it willbe needed to configure the BWP id to which the UE will hop to. Thefollowing message may be configured to the UE as part of RRCconfiguration settings since BWP will be configured to UE here:

  |  |  +-pusch-ConfigBasic : := SEQUENCE  /  /  /  +-n-BWP-HO : :=INTEGER  /  /  /  +-n-RB-HO : := INTEGER  |  |  |  +-hoppingmode : :=ENUMERATED [interSubFrame]  |  |  |  +-pusch-HoppingOffset : := INTEGER(0 . . 98) [4]  |  |  |  +-enable64QAM : := BOOLEAN [FALSE]

The following hopping types can be supported acrossslots/symbols/mini-slots:

-   -   Type 1: Frequency offset between the first time instant and the        second time instant is explicitly determined by DCI. This can be        within BWP or across BWP and depends on the number of RBs within        and across BWPs.    -   Type 2: Frequency offset between the first time instant and the        second time instant is configured by a predefined pattern. When        there is multiple BWPs, hopping is done from one BWP to another        BWP.

Some options can exist for PUCCH configuration as indicated by the gNBconfiguration:

a) PUCCH can be configured on all BWPs and this PUCCH can be usedwhenever there is specific BWP is activated for sending the UCI (uplinkcontrol information). If PUSCH is also configured for the same BWP thenPUSCH and PUCCH can be sent together. However if DFT-s-OFDM is used,then gNB can avoid configuring separate PUCCH and PUSCH regions insidethe same BWP for maintaining the single carrier property.

b) PUCCH is configured on only some BWPs or some fixed BWs (like adefault BWP). Then when PUSCH is configured on some BWPs without PUCCH,then UCI is sent on PUSCH with gNB configuration.

PUCCH configuration parameters within a BWP can be assumed to be same bythe UE to save signaling overhead, and if the PUCCH resource forHARQ-ACK is indicated by RRC signaling and/or L1 signaling, one PUCCHconfiguration is enough, the PUCCH configuration within any BWP is thesame, at least for the ones with same numerology. At least someparameters for PUCCH configuration can be same for BWPs which havedifferent numerology. For BWP with same numerology and different sizes,only exact location can change but the parameters remain same. This canbe configured by the network to the UE. This can be done at RRCconnection setup phase.

UL RBG Size Calculation

The UL RBG (resource block group) size will be

a) Indicated by DCI

b) Fixed based on UL BWP size

c) Based on a bitmap which can be used across multiple BWP; size ofbitmap is fixed by DCI

The uplink resource block groups of size P are numbered n_(RGB)=0, . . ., N_(RGB,BWP)

−1 in order of increasing physical resource-block number where uplinkresource block group H_(RGB,BWP) is composed of physical resource-blockindices within a BWP indexed as BWP in the equation shown. This equationcan be written per UL BWP. H_(RGB,BWP) contains PRBs indexed as shown inequation 5 below per BWP configured for the UL cases.

$\begin{matrix}\left\{ {{{\begin{matrix}{{{P \cdot n_{{RBG},{BWP}}} + i_{0} + i}\mspace{40mu}} & {{{{if}\mspace{14mu} N_{{RB},{BWP}}^{UL}\mspace{14mu}{mod}\; 2} = 0}\mspace{304mu}} \\{{{P \cdot n_{{RBG},{BWP}}} + i_{0} + i}\mspace{40mu}} & {{{if}\mspace{14mu} N_{{RB},{BWP}}^{UL}\mspace{14mu}{mod}\; 2} = {{1\mspace{14mu}{and}\mspace{14mu} n_{{RBG},{BWP}}} < {N_{{RBG},{BWP}}^{UL}\text{/}2}}} \\{{P \cdot n_{{RBG},{BWP}}} + i_{0} + i + 1} & {{{if}\mspace{14mu} N_{{RB},{BWP}}^{UL}\mspace{14mu}{mod}\; 2} = {{1\mspace{14mu}{and}\mspace{14mu} n_{{RBG},{BWP}}} \geq {N_{{RBG},{BWP}}^{UL}\text{/}2}}}\end{matrix}i} = 0},1,\ldots\;,{{P - {1{where}\mspace{14mu} i_{0}}} = {\left\lfloor \frac{N_{{RB},{BWP}}^{UL}}{2} \right\rfloor - \frac{P \cdot N_{{RBG},{BWP}}^{UL}}{2}}}} \right. & \left\lbrack {{equation}\mspace{14mu} 5} \right\rbrack\end{matrix}$

SRS Configuration

A UE shall transmit Sounding Reference Symbol (SRS) on per active UL BWPSRS resources based on two trigger types:

-   -   trigger type 0: higher layer signaling    -   trigger type 1: DCI formats specific for FDD/TDD or frame        structure

In case both trigger type 0 and trigger type 1 SRS transmissions wouldoccur in the same slot/symbol in the same BWP, the UE shall onlytransmit the trigger type 1 SRS transmission on that BWP.

The SRS transmission BW is configured by higher layers per BWP. Thetransmission and measurement BW for SRS can be different within a BWP.The SRS transmission slots/symbols are configured by higher layers. A UEconfigured for SRS transmission on multiple antenna ports and for a sameUL BWP shall transmit SRS for all the configured transmit antenna portswithin symbol/slot configured by higher layers and the SRS transmissionbandwidth and starting physical resource block assignment within the BWPand the BWP itself are the same for all the configured antenna ports.

For a UE not configured for PUSCH/PUCCH transmission, the UE shall nottransmit SRS whenever SRS transmission on the active BWP and PUSCH/PUCCHtransmission carrying HARQ-ACK/positive SR/RI(rankindicator)/PTI(precoding type indicator)/CRI(csi-rs resource indicator)and/or PRACH happen to overlap in the same symbol and that can result inuplink transmissions beyond the UE's indicated UL BWP capability (i.e.,how many BWP can UE handle simultaneously) included in theUE-EUTRA-Capability. This capability can be within 1 numerology or evenacross numerologies.

The parameter srs-ConfigIndex-per-BWP tells the UE about the SRStransmission periodicity per configured BWP and depending on the activeBWP, the UE can transmit the SRS within the configured BW. The followingconfigurations for SRS may be configured along with BWP configurationfor the UE—

  | +-soundingRS-UL-ConfigDedicated : := CHOICE [setup] OPTIONAL:Exist || +-setup : := SEQUENCE | |  +-srs-BandwidthConfig-perBWP : :=ENUMERATED [bw0] | |  +-srs-HoppingBandwidth-perBWP : := ENUMERATED[hbw0] | |  +-fregDomainPosition-perBWP : := INTEGER (0 . . 23) [0] ||  +-srs-Periodicity-perBWP : := ENUMERATED [sc0] | |  +-duration-perBWP: := BOOLEAN [FALSE] | |  +-srs-ConfigIndex : := INTEGER (0 . . 1023)[0] | |  +-transmissionComb-perBWP-BWsize : := INTEGER (0 . . 1) [0] ||  +-cyclicShift : := ENUMERATED [cs0]

The transmission comb, UE-specific parameter transmissionComb ortransmissionComb-ap for periodic and each configuration of aperiodictransmission, respectively, provided by higher layers for the UE, andcan depend on the BW size of the BWP over which the UE will send the SRSsignaling. Depending on whether the configured BWP is used by otherusers, the transmission comb may be applied or not by the gNB. Even forthe case of partially overlapping BWP, the gNB may take a decision onthe same. An example SRS BW configuration can be indicated as table 1below, depending on the size of BWP configured for the SRS transmission.Table 1 shows SRS configuration based on a BWP and its size(BWP . . .size), when m_(SRS,)

and

TABLE 1 SRS bandwidth SRS- SRS- SRS- SRS- config- bandwidth bandwidthbandwidth bandwidth uration B_(SRS) = 0 B_(SRS) = 1 B_(SRS) = 2 B_(SRS)= 3 C_(SRS) m_(SRS,0) N₀ m_(SRS,1) N₁ m_(SRS,2) N₂ m_(SRS,3) N3 0 X1 N01Y1 N11 Z1 N21 Ul N31 1 X2 N02 Y2 N12 Z2 N22 U2 N32 2 X3 N03 Y3 N13 Z3N23 U3 N33 3 X4 N04 Y4 N14 Z4 N24 U4 N34 4 X5 N05 Y5 N15 Z5 N25 U5 N35 .. . . . . . . . . . . . . . . . . . . . N Xn N0n Yn N1n Zn N2n Un N3n

The frequency hopping parameter can be configured per BWP in a UEspecific manner.

Aperiodic SRS may be triggered per BWP by the PDCCH DCI. The DCIsignaling can indicate the:

-   -   srsBWP    -   srsTransmissionBW

as example parameters for the transmission of the SRS on a specific BWP.A UE configured for Aperiodic SRS transmission upon detection of apositive SRS request in slot #n shall commence SRS transmission in thefirst slot satisfying slot #n+k, k≥X; where X is fixed in specificationor configured by gNB based on UE capability, the UL BWP size, retuninglimits etc, and based on the Aperiodic SRS time domain configuration. Incase both periodic and aperiodic SRS transmissions would occur in thesame slot/symbol within a BWP, the UE shall only transmit the AperiodicSRS. A UE will not transmit SRS whenever SRS and a PUSCH transmissioncorresponding to a RAR grant or a retransmission of the same TB(transmission block) as part of the contention based RA procedurecoincide in the same slot/symbol and within a configured BWP.

Within a BWP UE may be configured srsTranmsisionBW and specifically tosupport wideband SRS (entire BWP) or narrowband SRS (within differentregions of BWP).

PUSCH Indication for RACH

RAR indicates the PUSCH allocation for the UE. This allocation can bedictated as an offset form the SS block used by the UE or from the RMSIlocation or from the RAR location of PDSCH etc. If it is different BWP,additional indication of the BWP offset along with RB offset may beindicated to the UE. Explicit BWP need not be configured for the UE.

Other BWP Issues

In the embodiments presented here, embodiments of solutions aredescribed for issues related to re-transmissions across bandwidth parts,numerologies used, HARQ procedures for the same, configurations for BWPfor carrier aggregation and some operations.

Re-transmissions across BWP should be allowed by the gNB configurationto a UE. A gNB may activate different and wider BWP compared to firsttransmission because the size of the transport block size can be same ordifference in time due to larger resource block allocations. A UE may beconfigured a wider BWP for retransmission as compared to initialtransmission. Adaptive HARQ procedures can be supported for 5G systemswherein the PDCCH configuration is supported and indicates theconfiguration for the retransmission. This can also include BWP for thecase of retransmission being different from initial one.

Retransmission from one BWP to another may involve a) same numerologyBWP for 1st transmission and retransmission and b) different numerologyfor the 1st transmission and retransmission. This can be valid for anyretransmission and not just the 1st retransmission. When numerology ischanging across BWP, then HARQ procedure is shared across numerologies.The time lag between the PDSCH and HARQ timing follows numerology of theBWP wherein HARQ will be transmitted. When numerology are differentbetween PDCCH and the scheduled transmission of the PDSCH which can beon a different BWP, the time granularity indicated in the DCI for thetiming relationship between the end of PDCCH and the correspondingscheduled transmission on a different BWP is based on the numerology ofthe scheduled transmission i.e., the activated BWP for thistransmission. The time granularity of a HARQ-ACK transmission, indicatedin the DCI scheduling the PDSCH, is based on the numerology of PUCCHtransmission which is configured in a specific BWP and follows the BWPused for PUCCH transmission. The numerology for the PUCCH transmissionis determined based on the UL BWP configured for the user and indicatedto the UE.

FIG. 21 illustrates an embodiment of a relationship between bandwidthparts of Pcell (primary cell, 2110) and Scell (secondary cell, 2120)according to the proposed invention. Cross BWP scheduling simultaneouslywith cross carrier scheduling will be supported for 5G systems via gNBconfiguration. In other words if BWP (e.g., BWP2, 2115) is configuredper carrier; then scheduling should account for same. Hence, the crosscarrier scheduling will now have to indicate the carrier identity viaCIF(carrier indicator field)/ARFCN(Absolute Radio Frequency ChannelNumber). The BWP configurations for the target cell have to be indicatedto the UE via Scell addition procedure. Then the scheduling will have tobe indicated to the UE in terms of the BWP identification of the targetcell (e.g., BWP1, 2125 of Scell 2120). The timing will follow the timingof the BWP configured on the Scell (PDCCH to PDSCH delay).

Scell measurements, Scell feedback etc will happen based on the BWPconfigurations obtained. Initial configurations are via Pcell. Initialconfiguration can be changed to RRC signaling on Scell for later stages.CSI-RS measurements for the Scell will be done within the BWP activatedfor the UE. For reliable measurements, a UE may be configured with thefull Scell BW for full measurements if only CSI-RS measurements are tobe relied on.

PRB Indexing

Common and UE specific indexing are needed for different purposes tosupport wideband operations in 5G systems. Common indexing is good forsupporting BWP configuration, reference signal generation, search spaceconfigurations for the group common PDCCH among others. The UE specificindexing is good for UE specific search space, UE specific resourceallocation, among others.

Common PRB indexing is based on a numerology which can be one among thefollowing options:

-   -   Numerology of the SS block/PBCH used for that carrier and the UE        used for camping on the cell    -   Numerology of RMSI in case it is different from the SS block    -   Numerology indicated via RRC connection setup    -   Numerology indicated via RMSI    -   Numerology indicated via PBCH    -   Numerology indicated via L1 signaling, in case dynamic        indication is supported    -   In case of multiple SS blocks present inside a wideband carrier,        then the numerology of the default SS block may be assumed by        the UE    -   In case of multiple SS blocks present inside a wideband carrier,        then the numerology of an SS block indicated by the gNB to the        user can be used for indexing.    -   Numerology indicated via Msg4 in RACH procedure, if supported

Depending on the gNB configuration, one of these options may beconfigured by the gNB to a UE. If none of them is explicitly indicated,the UE can use the default numerology of the SS block it used forcamping on the cell.

When multiple SS blocks exist in the wideband, the referencepoint—should be common across all SS blocks in order to support commonoperations across the whole of wideband the UE is monitoring. Since thesame UE is monitoring the entire wideband and multiple SS blocks, it iscrucial to support common indexing. This common indexing must besupported from a reference location. This reference location can be anSS block, RMSI location, center of wideband carrier, center of a narrowband carrier among others. Considering that different users finddifferent SS blocks inside a wideband, a common location is preferredacross these SS blocks for indexing in order to avoid mismatch amongdifferent UEs about the mapping for RS, BWP configuration and searchspace configurations. This common location be indicated to the UE via:

-   -   PBCH        -   If needed for RMSI decoding; such as tracking RS;        -   Else if PDCCH DMRS is sufficient for SIB decoding etc. then            no need    -   RMSI        -   If needed for PRACH procedure such as PRACH region; RAR            decoding etc.        -   But RAR decoding CORESET same as initial access->no more            indication        -   PRACH region->indicated as offset from RMSI location; no            special care needed        -   RMSI PDCCH indicates PDSCH and hence this indication is            inside the PDSCH for RMSI    -   Via PRACH Msg4 after contention resolution    -   Via OSI—other system information/on-demand system information        when a UE can request for the same    -   RRC Connection establishment        -   CSI-RS necessity; PDCCH; BWP configuration are done only            after this stage        -   Really needed post this stage in connection establishment        -   Seems this is enough    -   Via RRC signaling        -   Can be changed in online manner based on number of UE etc by            the gNB        -   Signaling semi-static manner to UE

The reference point can be center of wideband carrier as it will becommon for all the potential SS blocks in this wideband spectrum.

Supporting Carriers Without SS Blocks

Potential Deployment Setting—Intra-band non-contiguous CA (carrieraggregation)

FIG. 22 illustrates an embodiment of supporting carriers withoutsynchronization signal blocks according to the proposed invention. TheFIG. 22 shows a potential deployment setting wherein operator A hasnon-contiguous spectrum (2210). A typical operating setting for thissituation is intra-band CA. However the conventional LTE mechanismforces each part of the Operator A's spectrum (2210) to carry an synchsignal and each will be configured as a cell namely Pcell and Scell.However, there may be some cases wherein one part of the Operator A'sspectrum (2210) may not be able to support a SS signal due to anotheroperator B's spectrum (2220) between the aggregated spectrum bands. Inanother case when the intraband CA can be supported by using 1 RF chain,the presence of multiple synch signals in each part of the spectrum isnot obvious and also deemed waste of resources. In such cases, it wasdeemed feasible to support a carrier with synch signals and hence thiscalls for a non-traditional CA operational scenario.

Since SS signals are not supported, this carrier cannot be treated forinitial access and cannot exist in stand alone mode. It is onlyactivated by the Pcell and but it can be configured and used as a Scell.However no mobility is supported on same via SS signals. However, for 5Gsystems CSI-RS signals are also configured and can support L3 mobilitymeasurements. The timing reference for this CSI-RS for such a carriercan be inferred from the SS signals of the primary carrier. Themeasurements needed for addition of this Scell can be either CSI-RSmeasurements or the gNB can blindly configure the same for a UE. RRCsignaling can be used to configure the CSI-RS measurements and provideany feedback between UE and gNB for this carrier. CSI-RS configurationfor inter-frequency measurement can be used to measure the RSRP or cellquality of a carrier without SS block, if network requires measurementresults before SCell addition.

Such a carrier has no cell-Id and all indication for this Scell will bevia carrier indicator field which is made of the ARFCN of this carrier.The configured CSI-RS can be used for Scell addition and release similarto the regular CA framework. Beam management etc. may be supported onthis carrier/Scell via use of CSI-RS only. In order to satisfy themeasurement accuracy obtained via SS blocks, the CSI-RS configurationsuch as time and frequency density for this Scell (without SS block) canbe different from the Pcell. Note that a UE cannot camp on this cellwithout the Pcell and is not self-discoverable.

FIG. 23 illustrates a terminal according to an embodiment to the presentdisclosure.

Referring to FIG. 23, the terminal (2300) includes a transceiver (2310),a controller (2320) and a memory (2330). The terminal (2300) in FIG. 23may be referred to as a user equipment (UE). Alternatively, thetransceiver may be implemented as a transmitter and a receiver, and eachcomponent may be implemented through one or more processors.

FIG. 24 illustrates a base station according to an embodiment of thepresent disclosure.

Referring to FIG. 24, the base station (2400) includes a transceiver(2410), a controller (2420) and a memory (2430). The base station (2400)in FIG. 24 may be referred to as a eNB, a gNB or a TRP (transmission andreception point). Alternatively, the transceiver may be implemented as atransmitter and a receiver, and each component may be implementedthrough one or more processors.

The above-described embodiments of the present disclosure and theaccompanying drawings have been provided only as specific examples inorder to assist in understanding the present disclosure and do not limitthe scope of the present disclosure. Accordingly, those skilled in theart to which the present disclosure pertains will understand that otherchange examples based on the technical idea of the present disclosuremay be made without departing from the scope of the present disclosure.

While the present disclosure has been particularly shown and describedwith reference to certain embodiments thereof, it will be understood bythose of ordinary skill in the art that various changes in form anddetails may be made therein without departing from the spirit and scopeof the present disclosure as defined by the following claims and theirequivalents.

1. A method performed by a terminal in a wireless communication system,the method comprising: receiving, from a base station, a control messageincluding first information associated with a time domain position of atleast one synchronization signal block (SSB) in an SSB burst and secondinformation associated with a periodicity for the at least one SSB;identifying whether a physical downlink shared channel (PDSCH) resourceallocation overlaps with a resource for the at least one SSB, based onthe first information and the second information; identifying a physicalresource block (PRB) including the resource for the at least one SSB, incase that the PDSCH resource allocation overlaps with the resource forthe at least one SSB; and receiving, from the base station, downlinkdata based on the PDSCH resource allocation, by considering that a ratematching is performed on the identified PRB in a symbol in which the atleast one SSB is received.
 2. The method of claim 1, wherein a number ofthe at least one SSB in the SSB burst and a time domain position foreach of the at least one SSB are identified by the first information. 3.The method of claim 1, wherein the control message is received by aradio resource control (RRC) signaling configuring a cell specificparameter for the terminal.
 4. The method of claim 1, wherein the ratematching is further performed on a demodulation reference signal (DMRS)associated with the PDSCH resource allocation, and wherein informationon a location of the DMRS is indicated by the base station.
 5. A methodperformed by a base station in a wireless communication system, themethod comprising: transmitting, to a terminal, a control messageincluding first information associated with a time domain position of atleast one synchronization signal block (SSB) in an SSB burst and secondinformation associated with a periodicity for the at least one SSB;identifying whether a physical downlink shared channel (PDSCH) resourceallocation overlaps with a resource for the at least one SSB, based onthe first information and the second information; performing a ratematching on a physical resource block (PRB) including the resource forthe at least one SSB in a symbol in which the at least one SSB istransmitted, in case that the PDSCH resource allocation overlaps withthe resource for the at least one SSB; and transmitting, to theterminal, downlink data based on the PDSCH resource allocation.
 6. Themethod of claim 5, wherein a number of the at least one SSB in the SSBburst and a time domain position for each of the at least one SSB areidentified by the first information.
 7. The method of claim 5, whereinthe control message is transmitted by a radio resource control (RRC)signaling configuring a cell specific parameter for the terminal.
 8. Themethod of claim 5, wherein the rate matching is further performed on ademodulation reference signal (DMRS) associated with the PDSCH resourceallocation, and wherein information on a location of the DMRS isindicated to the terminal.
 9. A terminal in a wireless communicationsystem, the terminal comprising: a transceiver configured to transmit orreceive a signal; and a controller coupled with the transceiverconfigured to: receive, from a base station, a control message includingfirst information associated with a time domain position of at least onesynchronization signal block (SSB) in an SSB burst and secondinformation associated with a periodicity for the at least one SSB,identify whether a physical downlink shared channel (PDSCH) resourceallocation overlaps with a resource for the at least one SSB, based onthe first information and the second information, identify a physicalresource block (PRB) including the resource for the at least one SSB, incase that the PDSCH resource allocation overlaps with the resource forthe at least one SSB, and receive, from the base station, downlink databased on the PDSCH resource allocation, by considering that a ratematching is performed on the identified PRB in a symbol in which the atleast one SSB is received.
 10. The terminal of claim 9, wherein a numberof the at least one SSB in the SSB burst and a time domain position foreach of the at least one SSB are identified by the first information.11. The terminal of claim 9, wherein the control message is received bya radio resource control (RRC) signaling configuring a cell specificparameter for the terminal.
 12. The terminal of claim 9, wherein therate matching is further performed on a demodulation reference signal(DMRS) associated with the PDSCH resource allocation, and whereininformation on a location of the DMRS is indicated by the base station.13. A base station in a wireless communication system, the base stationcomprising: a transceiver configured to transmit or receive a signal;and a controller coupled with the transceiver configured to: transmit,to a terminal, a control message including first information associatedwith a time domain position of at least one synchronization signal block(SSB) in an SSB burst and second information associated with aperiodicity for the at least one SSB, identify whether a physicaldownlink shared channel (PDSCH) resource allocation overlaps with aresource for the at least one SSB, based on the first information andthe second information, perform a rate matching on a physical resourceblock (PRB) including the resource for the at least one SSB in a symbolin which the at least one SSB is transmitted, in case that the PDSCHresource allocation overlaps with the resource for the at least one SSB,and transmit, to the terminal, downlink data based on the PDSCH resourceallocation.
 14. The base station of claim 13, wherein a number of the atleast one SSB in the SSB burst and a time domain position for each ofthe at least one SSB are identified by the first information.
 15. Thebase station of claim 13, wherein the control message is transmitted bya radio resource control (RRC) signaling configuring a cell specificparameter for the terminal.
 16. The base station of claim 13, whereinthe rate matching is further performed on a demodulation referencesignal (DMRS) associated with the PDSCH resource allocation, and whereininformation on a location of the DMRS is indicated to the terminal.